Fix CI and update for recent python releases#178
Merged
areski merged 5 commits intoareski:developfrom Oct 23, 2025
Merged
Conversation
Owner
|
@ngoldbaum Thanks for that |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
It looks like recent releases of setuptools have caused the CI to bitrot a little.
setup.py testno longer works, so I had to replace that with an explicitunittestinvocation. Recent versions of setuptools also complain about the license trove classifier, so I removed that.I also dropped Python 3.7 tests (it's not installable on recent setup-python versions) and added 3.13, 3.14, and 3.14t tests.